Repository navigation
Move TigerMap deployment to TigerApps-Combined - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TigerMap's API is moving from its dedicated EC2 instance to TigerApps-Combined. Point the documented deployment IAM policy and host configuration at Combined, and allow manually triggering the existing validation and deployment workflow.
The API service paths, local SQLite storage, public Elastic IP, and Cloudflare Pages origin remain unchanged. Deployment continues to restart only
tigermap-apion the shared host. Live repository variables and IAM policy are updated as part of the migration.Validation:
git diff --check; full CI and an actual deployment to Combined will be verified during cutover.